Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Adds a direct link to the span in the results table:

Currently it's possible to only navigate to the start of a trace, but that's inconvenient if you want to go directly to the span. Sometimes this is become a huge pain if the trace contains many spans.
I tried to add the link to the
SpanIdcolumn, since it makes more sense IMO, but I wasn't able to make it work.(In this example
TraceId=d7a3ce97bcf9758befb3013e3540a568,SpanId=ad9771c2c5a05563)The issue is that the resulting link URL has
"traceId":"<SpanId>", while the correct link URL has it right:(below just the most important differences):Full link URLs
You can find a
TODOin the code for the broken SpanId column.I would really appreciate some guidance on how to make the link on SpanId work, because I believe it would be the best user experience 😉.
If it's not possible, the link on the TraceId column would still be a good solution and certainly an improved UX in case of large traces.